ot over-ride the over-ride? Or, put
>> another way, would the following not make sense:
>> if --synctex is used on the command line
>> create synctex file
>> else if --nonstop is used on the command line
>> do not create the synctex file
>> else if \setupsynctex[...
rtparagraphs
Command/ startparallel
Command/ startplacefloat
Command/ startplacepairedbox
Command/ startsection
Command/ startsectionblock
Command/ startstartstop
Command/ startstop
Command/ startstyle
Command/ starttabulate
Command/ starttextbackground
Command/ starttyping
Command/ startviewerlayer
he command line
> do not create the synctex file
> else if \setupsynctex[...] is used in the source file
> create the synctex file
> else
> do not create the synctex file
>
> > - the ma
On 4/6/24 11:43, madiazm.eo...@gmail.com wrote:
> Hi everyone,
Hi Miguel,
> […]
> Am I missing something on the use of this ligature?
I don’t think so.
In some cases you may not get the ligature for a good reason:
\starttyping
program --option=value file.ext
\stoptyping
It w
rder to get an idea of how we will get rid of the disturbing formulas, you
can load the module:
\starttyping
\usemodule[math-goodriddance]
\stoptyping
Until becoming the default setting, the command \typ {\goodriddancemath} will
bring you into \MLTX\ mode while \typ {\badriddancemath} will bring you
Pablo Rodriguez via ntg-context schrieb am 17.03.2024 um 17:38:
Dear list,
I have the following sample (which was on the way of showing another issue):
\starttext
a
\starttyping
b
\stoptyping
c
\startfootnote
a
\starttyping
b
\stoptyping
c
\stopfootnote
Dear list,
I have the following sample (which was on the way of showing another issue):
\starttext
a
\starttyping
b
\stoptyping
c
\startfootnote
a
\starttyping
b
\stoptyping
c
\stopfootnote
\stoptext
Current latest (from 2024.03.11 09:34) breaks compilation with both
\NC d \NC= e + f \NR[+]
\NC g \NC= h + i
\stopalign\stopformula
\samplefile{knuth}
\section{“I expect to see \tex{noalign} only after the \tex{cr} of an alignment.”}
\starttyping
\samplefile{knuth}
\startformula
\text{something} + \text{really} + \text{really} + \t
currentdate,
%D copyright={Aditya Mahajan}]
%D This metapost module is inspired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput
lp me please?
>
>
> \starttyping
> 0! := 1
> (n + 1)! := (n + 1) n!
> \stoptyping
Or:
\startformula
\startalign[n=1,align={1:left}]
\NC 0! := 1\NR
\NC (n + 1)! := (n + 1) n!\NR
\stopalign
\stopformula
https://wiki.context
> On 05/01/2024 14:27, Ursula Hermann wrote:
>
>> Can someone help me please?
>
>
> \starttyping
> 0! := 1
> (n + 1)! := (n + 1) n!
> \stoptyping
Or:
\startformula
\startalign[n=1,align={1:left}]
\NC 0! := 1\NR
\NC (n + 1)! := (n + 1) n!\NR
On 05/01/2024 14:27, Ursula Hermann wrote:
This is a formular with factorial.
0! := 1
(n + 1)! := (n + 1) n!
this looks more like a code example than a math formula
Can someone help me please?
\starttyping
0! := 1
(n + 1)! := (n + 1) n!
\stoptyping
l) to
include symbols for the control characters.
In typo-rep there is also
%D \starttyping
%D \definefontfeature[default][default][mode=node,formatters=strip]
%D \stoptyping
You included some notes about Khaled, so I guess he faced the same issue. His
Amiri font displays the symbols by default, a
acters.
In typo-rep there is also
%D \starttyping
%D \definefontfeature[default][default][mode=node,formatters=strip]
%D \stoptyping
You included some notes about Khaled, so I guess he faced the same issue. His
Amiri font displays the symbols by default, as do other Arabic fonts.
(It seems he
of the
\everyinitializeverbatim register because it is used for
inline and display verbatim. A better place to add the option is
\buff_verbatim_initialize_typing_two for \starttyping
and \buff_verbatim_initialize_type_two for \type.
ok
zeverbatim
and then
\startsetups typing:mine
\setbreakpoints[compound]
\stopsetups
with
\starttyping[lines=yes,setups=typing:mine]
I need Wolfgang to check it for possible interferen
gparameter
\to \everyinitializeverbatim
and then
\startsetups typing:mine
\setbreakpoints[compound]
\stopsetups
with
\starttyping[lines=yes,setups=typing:mine]
I need Wolfgang to check it for possible interferen
the truth: waste-not-want-not \par
2. This is the truth: waste/not/want/not \par
3. This is the truth: waste+not+want+not \par
4. This is the truth: waste(not(want(not)) \par
5. This is the truth: ((waste)not)want)not
\starttyping[lines=yes]
1. Thisisthetruth:waste-not-want-not \par
2. Thisisthet
explain?
Hraban
Am 15.08.23 um 22:31 schrieb Hans Hagen via ntg-context:
Hi,
Especially for long verbatim lines we now can do this:
\starttext
\setupalign[hangright]
\starttyping
test test test test test test test test test test test test test test
test test test test test test test test
Hi,
Especially for long verbatim lines we now can do this:
\starttext
\setupalign[hangright]
\starttyping
test test test test test test test test test test test test test test
test test test test test test test test test test test test test
test test test test test test test test test test
Thanks Hans!
Le 4/08/23 à 23:21, Hans Hagen a écrit :
On 8/4/2023 7:42 PM, Alex Leray wrote:
Hello,
I'm trying to figure out why this is not working (whereas
\startlines\stoplines works):
```
\definehead[poem][section]
\setuphead[poem][beforesection={\starttyping},
aftersection
On 8/4/2023 7:42 PM, Alex Leray wrote:
Hello,
I'm trying to figure out why this is not working (whereas
\startlines\stoplines works):
```
\definehead[poem][section]
\setuphead[poem][beforesection={\starttyping}, aftersection={\stoptyping}]
\starttext
\startpoem[title={Glijden}][]
Lorem
Hello,
I'm trying to figure out why this is not working (whereas
\startlines\stoplines works):
```
\definehead[poem][section]
\setuphead[poem][beforesection={\starttyping}, aftersection={\stoptyping}]
\starttext
\startpoem[title={Glijden}][]
Lorem ipsum dolor sit amet consectetur.
\stoppoem
g I had never thought of, using PDF comments,
thanks!.
It's a really nice approach, though weirdly it doesn't work on Okular
(Linux+KDE)
for me, even though attachments worked fine. I'll try and see why that
is.
What I had in mind was rather the following:
\starttext
\starttyping[space=on]
Dear list,
I have the following sample:
\setuplinenumbering[typing]
[step=3]
\starttext
\starttyping[numbering=line]
Line
Line
Line
\stoptyping
\stoptext
Which \setuplinenumbering is applied to typing fragments?
Just in case my question isn’t clear: how can I get
Am 05.08.22 um 20:07 schrieb Wolfgang Schuster via ntg-context:
juh+ntg-context--- via ntg-context schrieb am 05.08.2022 um 19:04:
\starttyping
foo
└── bar
├── baz
│ └── index.html
└── index.html
\stoptyping
The source code is generated with the linux command "tree".
juh+ntg-context--- via ntg-context schrieb am 05.08.2022 um 19:04:
Dear all,
I have this:
\starttext
\starttyping
foo
└── bar
├── baz
│ └── index.html
└── index.html
\stoptyping
\stoptext
The source code is generated with the linux command "tree".
The special
Dear all,
I have this:
\starttext
\starttyping
foo
└── bar
├── baz
│ └── index.html
└── index.html
\stoptyping
\stoptext
The source code is generated with the linux command "tree".
The special characters which indicate the folder depth are not displayed.
I gu
driguez
> Betreff: Re: [NTG-context] \startXML vs \startPARSEDXML
>
> On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> > Hi everyone,
> >
> > the wikipage on \starttyping
> > (https://wiki.contextgarden.net/Command/_starttyping
> > <https://wiki.cont
On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> Hi everyone,
>
> the wikipage on \starttyping
> (https://wiki.contextgarden.net/Command/_starttyping
> <https://wiki.contextgarden.net/Command/_starttyping>) says there are
> some dedicated commands, e.g. \startXML and
Hi everyone,
the wikipage on \starttyping
(https://wiki.contextgarden.net/Command/_starttyping) says there are some
dedicated commands, e.g. \startXML and \startPARSEDXML. How do they differ?
Best,
Denis
Ajith R via ntg-context schrieb am 01.01.2022 um 11:14:
For Malayalam, most often we would be expecting ligation to work even
within \starttyping \stoptyping.
You can anyway make a typescript that matches your needs.
Don't know how. Can you point towards a documentation?
You can use
On 1/1/2022 11:14 AM, Ajith R wrote:
Don't know how. Can you point towards a documentation?
\type-imp-*
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt |
On Sat, 1 Jan 2022 11:04:03 +0100
Hans Hagen wrote:
> quick and dirty
>
> \setuptyping[style={\definedfont[Mono*malayalam-two]}]
>
> \starttyping
> മലയാളലിപികളുടെ ആവൃത്തി നിർണ്ണയം
> \stoptyping
That was a quick fix. Yes, it is working.
> If the need for features i
the command pair \starttyping \stoptyping,
conjuncts are not formed as outside the command pair. Is it possible to
enforce [features=malayalam-two] even inside \starttyping \stoptyping
command pair?
quick and dirty
\setuptyping[style={\definedfont[Mono*malayalam-two]}]
\starttyping
മലയാളലിപികളുടെ
Hi,
I am trying to prepare a moderate sized document in Malayalam using
Context. Overall I have been successful. However, there are a few rough
edges for which I need help. This is the sixth problem I face.
If I use Malayalam inside the command pair \starttyping \stoptyping,
conjuncts
{\typebuffer}:
\typebuffer[javacode]
\type{\typing}:
\starttyping
try {
final var num = stack.pop();
if( num != null ) {
stack.push( blah );
}
return true;
}
\stoptyping
\type{\typefile}:
\typefile{t.java}
\stoptext
There appear to be two issues.
First, \typefile produces what I'd
The problem also concerns \starttyping:
\starttext
.
\startluacode
context([[
\starttyping
\stoptyping
]])
\stopluacode
\stoptext
tex error > runaway error: end of file encountered
mtx-context | fatal error: return code: 256
%
\starttext
.
\startluacode
cont
Sylvain Hubert schrieb am 07.09.2021 um 13:38:
Thanks Wolfgang, this solves my problem.
But now I'm wondering why \starttyping[before=,after=] cannot do the same job?
Works here.
\starttext
Remove space below
\starttyping[before=,after=]
some
code
\stoptyping
\stoptext
Wolfgang
Sylvain Hubert via ntg-context schrieb am 07.09.2021 um 11:49:
Dear List,
How should we remove the vertical space above and below the following typing?
\starttext
Remove space below
\starttyping
some
code
\stoptyping
\stoptext
\setuptyping [before=,after=]
Wolfgang
Dear List,
How should we remove the vertical space above and below the following typing?
\starttext
Remove space below
\starttyping
some
code
\stoptyping
\stoptext
Thanks!
Best,
Sylvain
___
If your question
]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
example
\stoptyping
\stoptext
\definetextbackground
[Code]
[frame=on,
framecolor=black,
corner=round,
radius=10pt,
topoffset=10pt,
leftoffset=5pt,
background=color,
backgroundcolor=gray,
location=paragraph
]
\definetextbackground
[Code]
[frame=on,
framecolor=black,
%corner=0,
%offset=10pt,
background=color,
backgroundcolor=gray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
=on,
framecolor=black,
%corner=0,
%offset=10pt,
background=color,
backgroundcolor=gray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
example
\stoptyping
\stoptext
On 7/28/2021 10:12 PM, Wolfgang Schuster wrote:
2. Rather than adding a additional argument to \starttyping etc. provide
a \startnamedtyping with a mandatory argument with the name of the
instance.
ok, but i do need to check the before/after wrt setup
To save a few lines of code a flag (e.g
it.
\writestatus{loading}{ConTeXt Language Macros / Replacements}
\unprotect
\registerctxluafile{lang-rep}{autosuffix}
\definesystemattribute[replacements][public,global]
%D \startluacode
%D
%D -- todo: other nodes (prelude to more experiments with auto dropped caps)
%D
%D languages.replacem
> On 28 Jul 2021, at 13:13, Jeroen via ntg-context wrote:
>
> Is there a way to have two different styles of typing. I tried the following,
> but it does not seem to work.
>
> \setuptyping[abc][style=\ttx]
> \setuptyping[def][style=\ttxx]
>
> \starttext
>
> Am 28.07.2021 um 14:14 schrieb Jeroen via ntg-context :
>
> Is there a way to have two different types of typing. I tried the following,
> but it does not seem to work.
>
> \setuptyping[abc][style=\ttx]
> \setuptyping[def][style=\ttxx]
>
> \starttext
>
>
On 7/28/2021 2:14 PM, Jeroen via ntg-context wrote:
Is there a way to have two different types of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
text
text
\stoptyping
\starttyping[def
Is there a way to have two different types of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
text
text
\stoptyping
\starttyping[def]
text
text
\stoptyping
\stoptext
Is there a way to have two different styles of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
example
example
\stoptyping
\starttyping[def]
example
example
\stoptyping
\stoptext
Thanks
tdate,
%D copyright={Aditya Mahajan}]
%D This metapost module is inspired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput mp-s
module is inspired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput mp-sketch;
%D
%Dbeginfig(1)
%D sketchypaths; % Ma
ired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput mp-sketch;
%D
%Dbeginfig(1)
%D sketchypaths; % Make draw and fil
On 4/26/2021 12:23 PM, Floris van Manen wrote:
\starttext
\starttyping[escape=@]
1 137 26 25 > 1 69 32
2 @btex@bgroup@red@bf 137 @egroup@etex 26 25 > 1 69 32
3 @btex@bgroup@red@bf 137 @egroup@etex 26 25 > 1 69 32
4 137 26 25 > 1 69 32
Aparently all spaces after @etex get reduced to one only.
I'd expect that to happen inside @btex and @etex
\starttext
\starttyping[escape=@]
1 137 26 25 >1 69 32
2 @btex@bgroup@red@bf 137 @egroup@etex 26 25 >1 69 32
3 @btex@bgroup@red@bf 137 @egroup@etex
On 26/04/2021 10:59, Hans Hagen wrote:
\starttext
\starttyping[escape=/]
one two three
four /btex/bgroup/red five /egroup/etex six
seven eight nine
\stoptyping
\stoptext
That works indeed! Thanks.
Are there restriction on what context commands can be given inside the
bgroup? e.g. I tried
On 4/26/2021 10:25 AM, Floris van Manen wrote:
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
\starttext
\starttyping[escape
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
.Floris
> ... which means that you can use that at the context end as well
> > (old feature).
> > > Save the following as test.mkix (or add "% macros=mkix" as the
> > first line):
> > >
> > > ```
&g
ate, which is evaluated on the fly rather than when loading
> > > > a
> > > > file.
> > >
> > > define 'evaluated on the fly'
> >
> > Consider the following example:
> >
> > \enablemode[A]
> > \starttext
> > \start
example:
\enablemode[A]
\starttext
\startluatemplate
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stopluatemplate
\stoptext
What I am thinking is that \startluatemplate ... \stopluatemplate grabs the
content (like a buffer
ollowing example:
\enablemode[A]
\starttext
\startluatemplate
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stopluatemplate
\stoptext
What I am thinking is that \startluatemplate ... \stopluatemplate grabs the
content (like a buffer) and then processe
(old feature).
> Save the following as test.mkix (or add "% macros=mkix" as the
first line):
>
> ```
> \starttext
>
> \starttyping
> A and not B
> \stoptyping
>
> \starttyping
; ... which means that you can use that at the context end as well
> > (old feature).
> > > Save the following as test.mkix (or add "% macros=mkix" as the
> > first line):
> > >
> > > ```
> > > \starttext
>
t;% macros=mkix" as the
first line):
>
> ```
> \starttext
>
> \starttyping
> A and not B
> \stoptyping
>
> \starttyping
> not (A and not B)
> \stoptyping
>
> \stoptext
a neat application!
Th
n
> >> ...
> >> end
> >
> > ... which means that you can use that at the context end as well (old
> feature).
> > Save the following as test.mkix (or add "% macros=mkix" as the first
> line):
> >
> > ```
> > \starttext
> &
llowing as test.mkix (or add "% macros=mkix" as the first line):
```
\starttext
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stoptext
a neat application!
Hans
-
d "% macros=mkix" as the first line):
```
\starttext
\starttyping
A and not B
\stoptyping
\starttyping
not (A and not B)
\stoptyping
\stoptext
```
See the templates manual for more details:
https://www.pragma-ade.c
hr schrieb Philipp A. >:
>
>> Thank you, but whitespace is ignored in .bib file syntax. To prove that
>> whitespace handling isn’t the bug, just try accessing it:
>>
>> \startluacode
>> local current = publications.datasets.default
>> tex.print('\\starttyping')
he bug, just try accessing it:
>
> \startluacode
> local current = publications.datasets.default
> tex.print('\\starttyping')
> tex.print(table.serialize(current.luadata))
> -- to show that the key doesn’t contain weird invisible characters, I’ll
> type it here:
Thank you, but whitespace is ignored in .bib file syntax. To prove that
whitespace handling isn’t the bug, just try accessing it:
\startluacode
local current = publications.datasets.default
tex.print('\\starttyping')
tex.print(table.serialize(current.luadata))
-- to show that the key doesn’t
t; >
> > Why do pass a option for the typing environment to \starttext?
> >
> > > \definetextbackground[code][background=color, backgroundcolor=lightgray,
> > > frame=off, location=paragraph]
> > >
> > > \setuptyping[before={\startbackground[code]}
gt; > \definetextbackground[code][background=color, backgroundcolor=lightgray,
> > frame=off, location=paragraph]
> >
> > \setuptyping[before={\startbackground[code]}, after={\stopbackground}]
> >
> > \starttext[option=XML]
> > \starttyping
> > This is s
=paragraph]
\setuptyping[before={\startbackground[code]}, after={\stopbackground}]
\starttext[option=XML]
\starttyping
This is some code
a second line
\stoptyping
\stoptext
When I use \definetyping[Mytyping][option=XML] and then use \startMytyping ...
\stopMytyping nothing changes
; > > Aditya
> > > > > For example, take:
> > > > >
> > > > > \definetextbackground[code][background=color,
> > > > > backgroundcolor=lightgray,
> > > > > frame=off, location=paragraph]
> > > > >
>
t; > > > a
> > > > > > sidebar. No addition spacing / empty lines.
> > > > > A MWE will help...
> > > > >
> > > > > Aditya
> > > > For example, take:
> > > >
> > > > \definetextba
? I just want a background to these
and
a
sidebar. No addition spacing / empty lines.
A MWE will help...
Aditya
For example, take:
\definetextbackground[code][background=color, backgroundcolor=lightgray,
frame=off, location=paragraph]
\starttextbackground[code]
\starttyping
This is some code
, take:
> >
> > \definetextbackground[code][background=color, backgroundcolor=lightgray,
> > frame=off, location=paragraph]
> >
> > \starttextbackground[code]
> > \starttyping
> > This is some code
> > a second line
> > \stoptyping
> > \st
...
Aditya
For example, take:
\definetextbackground[code][background=color, backgroundcolor=lightgray,
frame=off, location=paragraph]
\starttextbackground[code]
\starttyping
This is some code
a second line
\stoptyping
\stoptextbackground
You missed the W (working) in MWE.
\definetextbackground
> > > sidebar. No addition spacing / empty lines.
> >
> > A MWE will help...
> >
> > Aditya
>
> For example, take:
>
> \definetextbackground[code][background=color, backgroundcolor=lightgray,
> frame=off, location=paragraph]
>
>
> Aditya
For example, take:
\definetextbackground[code][background=color, backgroundcolor=lightgray,
frame=off, location=paragraph]
\starttextbackground[code]
\starttyping
This is some code
a second line
\st
xtable()
context.startxrow()
context.startxcell()
context.starttyping()
context('1')
context.stoptyping()
context.stopxcell()
context.stopxrow()
context.stopxtable()
\stopluacode
% this does not
\startxtable
\startxrow
\startxcell
\starttyping
\setuptagging[state=start]
\starttext
\starttyping
mtxrunjit --generate
\stoptyping
\startitemize[n]
\startitem a\stopitem
\stopitemize
\stoptext
I have no idea why.
because \doverbatimspace is defined in a way that will look ahead
\unexpanded\def
ext
\starttyping
mtxrunjit --generate
\stoptyping
\startitemize[n]
\startitem a\stopitem
\stopitemize
\stoptext
I have no idea why.
Many thanks for your help,
Pablo
> well, the clue is there: you have
>
> you have a \hskip or \vskip someplace that is not properl
Henning Hraban Ramm schrieb am 01.06.2020 um 20:22:
Hi,
I finally wanted to attack CG journal 2019 again and stumble upon this error:
If an article contains several \starttyping ... \stoptyping examples with a
textbackground, it sometimes fills the whole column (pagecolumns). It doesn’t occur
Hi,
I finally wanted to attack CG journal 2019 again and stumble upon this error:
If an article contains several \starttyping ... \stoptyping examples with a
textbackground, it sometimes fills the whole column (pagecolumns). It doesn’t
occur if the "typing" is at top or bottom of
> Am 24.05.2020 um 14:04 schrieb Floris van Manen :
>
> Does anyone know how to activate/use the pretty printing of python code?
>
> \starttyping[option=python]
>
> does not work.
No, ConTeXt supports only TeX, XML, MetaPost and Lua.
Try Aditya’s vim module:
https
Does anyone know how to activate/use the pretty printing of python code?
\starttyping[option=python]
does not work.
.Floris
pEpkey.asc
Description: application/pgp-keys
___
If your question is of interest
the C example, however this does not seem to work. No
> > formatting is applied to my keywords.
>
> Can you provide a minimal example what you have tried.
>
> > Just wondering if the way to do it has changed or if there are other
> > examples I could look at to compare with what I'm doi
.
\starttext
\starttyping[escape=yes]
This is /BTEX\bf formatted/ETEX text.
\stoptyping
\starttyping[escape={<<,>>}]
This is <<\bf formatted>> text.
\stoptyping
\starttyping[escape={}]
This is text.
\stoptyp
Hi,
in the following code example the result from \type lacks the space
between \cmd and the following left bracket.
\starttext
\starttyping
\cmd [...]
\stoptyping
\type{\cmd [...]}
\stoptext
Wolfgang
Wolfgang will cook up a patch ...
The best solution is to remove the values from all three keys because
for now each of them is applies twice (even the style).
\setuptyping
[before=\hairline,
after=\hairline,
style=\tt\em]
\starttext
\starttyping[option=tex]
\donothing
\stoptyping
, before=\startEXAMPLE, after=\stopEXAMPLE]
\starttext
\starttyping
A = B + C
\stoptyping
\stoptext
gives the attached output where the background is repeated twice. The
bug is present with both mkiv and ltmx.
Aditya
Hi,
The following minimal example:
\definetextbackground
[EXAMPLE]
[
location=paragraph,
rulethickness=1pt,
leftoffset=5em,
rightoffset=0mm,
]
\setuptyping[option=tex, before=\startEXAMPLE, after=\stopEXAMPLE]
\starttext
\starttyping
A = B + C
]
\setuptyping[indentnext=auto]
\starttext
\starttyping
Typing
\stoptyping
Paragraph
\starttyping
Typing
\stoptyping
Paragraph
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add
=yes]
\setupbodyfont
[dejavu,10pt]
\showglyphs
\starttyping
푷₂₀(0), ∀²푥⁰⁺²₂₀: 푷₂₀(푥⁰⁺²₂₀) ⇒ 푷₂₀(s(푥⁰⁺²₂₀)) ⊢ ∀¹푦⁰⁺¹₂₀ 푷₂₀(푦⁰⁺¹₂₀)
\stoptyping
\startformula
푷₂₀(0), ∀²푥⁰⁺²₂₀: 푷₂₀(푥⁰⁺²₂₀) ⇒ 푷₂₀(s(푥⁰⁺²₂₀)) ⊢ ∀¹푦⁰⁺¹₂₀ 푷₂₀(푦⁰⁺¹₂₀)
\stopformula
ah, so it's time for some new (undocumented) math
[stixtwotext]
>> [range={0100-10},factor=1] [force=yes]
>> \setupbodyfont
>> [dejavu,10pt]
>> \showglyphs
>> \starttyping
>> 푷₂₀(0), ∀²푥⁰⁺²₂₀: 푷₂₀(푥⁰⁺²₂₀) ⇒ 푷₂₀(s(푥⁰⁺²₂₀)) ⊢ ∀¹푦⁰⁺¹₂₀ 푷₂₀(푦⁰⁺¹₂₀)
>> \stoptyping
>> \startformula
>> 푷₂₀
(though not in the case below), and that is used in tensor
notation. In TeX, the original suggestion is to use {} in such a case.
—
\definefontfallback
[Mono] [stixtwotext]
[range={0100-10},factor=1] [force=yes]
\setupbodyfont
[dejavu,10pt]
\showglyphs
\starttyping
푷₂₀(0), ∀²푥⁰⁺²₂₀: 푷
example below math mode. But actually, there may be a semantic difference
between the order (though not in the case below), and that is used in tensor
notation. In TeX, the original suggestion is to use {} in such a case.
—
\definefontfallback
[Mono] [stixtwotext]
[range={0100-10},fact
1 - 100 of 566 matches
Mail list logo
